Thanks! Not a complete review, but we require Anys to be documented (either using a comment or using an appropriate type alias). I noticed that you added Any annotations to a few kwargs arguments which are - I suspect - forwarded to another function. In this case, we could copy the arguments over (or leave kwargs unannotated for now).

I'll review these again and document where I can. I certainly may have missed some forwarded calls in this project.

However, there are some bad practices in the codebase, like a ABCs with an empty (non-abstract) __init__ method with **kwargs and no types. I think I may just remove these from the annotations instead.

However, there are some bad practices in the codebase, like a ABCs with an empty (non-abstract) init method with **kwargs and no types. I think I may just remove these from the annotations instead.

You could either remove them if you think that no valid code should call __init__ with arguments, or you could use _typeshed.Unused to mark that fact.

You could either remove them if you think that no valid code should call __init__ with arguments, or you could use _typeshed.Unused to mark that fact.

The project isn't that well structured, I am not confident enough to say it'll never be called with arguments. So I removed it from the type hints altogether.

According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉